Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

Deploying generated-4GL static objects

The main complication in the deployment of generated-4GL static objects is that you must also consider deployment of the dynamic equivalents in the process. You must also take care to deploy the r-code for generated-4GL objects in a directory specified by Dynamics. There are also guidelines on when it is necessary to regenerate and redeploy these objects. This section describe all of these issues.

What to deploy

Table D–2 shows the minimum files that you need to deploy to the client for a given object, depending on the state of the object. As minimum files, ADO indicates the deployment datasets for the abstract definitions in the Repository. PGEN indicates the source and r-code files for the generated-4GL static object equivalents.

Table D–2: Minimum files to deploy for generated-4GL static objects

Object state	Minimum files to deploy
New object.	ADO, PGEN
Modified object, including properties or contained instances, but excluding changes to the object path.	PGEN
Modified object, including properties, contained instances, and changes to the object path.	ADO, PGEN

While, under some circumstances, you can deploy only the PGEN files for generated-4GL objects, Progress Software Corporation recommends that you always deploy both the ADO and PGEN files. Otherwise, you risk losing track of the differences between them. If you find it expedient to deploy only the PGEN files in order to provide a fast and temporary fix or patch, deploy the ADO to the client as soon as possible to maintain consistency between the dynamic and generated equivalents of the object.

Where to deploy

Typically, you deploy the source code files for generated-4GL objects to directories as specified by the object path, per object. You must deploy the r-code for these objects into the gen subdirectory of the client cache directory (typically, OpenEdge_Install\src\dynamics\ry\clc\). Dynamics ignores the PROPATH and looks only in the client cache deployment area for any generated-4GL object r-code that it needs to execute.

When to deploy

After the initial deployment, you must regenerate and redeploy generated-4GL static objects when one or more of the following changes occur:

Information about the object itself, such as its object path.
Changes to super procedures, depending on how you generate the object’s super procedures (invoked by the object constructor, generated in-line, or generated as an ADM property).
Properties of the object itself.
Information about the object’s pages and links (any addition, modification, or removal of the links).
Information about the contained instances, including names, attributes, and UI events.
For dynamic viewers, any information about the contained objects’ master objects. (The DataField and local widgets (not SmartDataFields) are not procedure based. So, all master information must be generated into the viewer. This is also true of class information for the contained widgets. Classes affected include the DataField class and all its subclasses, and the ProgressWidget class and all its subclasses.)